System for communicating labeled routing trees to establish preferred paths and source routes with local identifiers in wireless computer networks

ABSTRACT

One or more labeled routing trees (LRTs) are produced at a router of a computer network according to a shortest path determination made over a partial topology graph of the network, which graph is produced according to knowledge of adjacent links of the router and one or more LRTs of neighboring routers. The LRTs of the router may be updated in response to receipt of routing state update messages, and such messages may include local link identifiers assigned by a head of a link to which the identifiers pertain, and node parameters of a tail of the link to which the local link identifiers pertain. The routing state update messages may be transmitted within the network: (i) in response to a new destination node being detected by an existing node within the network, (ii) in response to a destination becoming unreachable by a collection of the existing nodes, (iii) in response to the change in the cost of a path to at least one destination exceeding a threshold and/or (iv) in situations where a routing loop may be encountered among two or more of the nodes of the network (e.g., at times when a path implied in the LRT of the router leads to a loop).

STATEMENT OF GOVERNMENT LICENSE RIGHTS

[0001] The United States Government has a paid-up license in portions of this invention and the right in limited circumstances to require the patent owner to license others on reasonable terms as provided for by the terms of Contract No.: DAAH01-98-C-R005, awarded by the U.S. Army Aviation & Missile Command.

FIELD OF THE INVENTION

[0002] The present invention relates to routing protocols in computer networks, and more particularly, routing protocols in ad hoc networks with radio links.

BACKGROUND

[0003] Multi-hop packet-radio networks, or ad hoc networks, consist of mobile hosts interconnected by routers that can also move. The deployment of such routers is ad hoc and the topology of such networks is very dynamic, because of host and router mobility, signal loss and interference, and power outages. In addition, the channel bandwidth available in ad hoc networks is relatively limited compared to wired networks, and untethered routers may need to operate with battery-life constraints. In these networks, routing must preferably be accomplished using as few a number of control messages and neighbor-to-neighbor handshakes as possible, in order to conserve channel bandwidth for user data and preserve the battery life of untethered nodes. Because of the dynamics of the topology in an ad hoc network, broadcast radio links are preferable for interconnecting routers without the need for topology planning.

[0004] Routing protocols for computer networks can be categorized according to: (a) the type of information the protocols use to compute preferred paths, and (b) the way in which routers obtain routing information. In terms of the type of information used by routing protocols, routing protocols can be classified into link-state protocols and distance-vector protocols. Routers running a link-state protocol use topology information to make routing decisions; routers running a distance-vector protocol use distances and, in some cases, path information, to destinations to make routing decisions.

[0005] In terms of the way in which routers obtain information, routing protocols have been classified as either table-driven or on-demand. In an on-demand routing protocol, routers maintain path information for only those destinations that they need to contact as a source or relay of information. The basic approach consists of allowing a router that does not know how to reach a destination to send a flood-search message to obtain the path information it needs. One of the first routing protocols of this type was proposed to establish virtual circuits in the MSE network, see V.O.K. Li and R. Chang, “Proposed routing algorithms for the US Army mobile subscriber equipment (MSE) network,” Proc. IEEE MILCOM'86, Monterey, Calif., October 1986, and there are several other, recent examples of this approach (e.g., AODV, see C. Perkins, “Ad Hoc On Demand Distance Vector (AODV) Routing,” draft-ietf-manet-aodv-00.txt, November 1997; ABR, see C -K. Toh, “Wireless ATM & Ad Hoc Networks,” Kluwer, November 1996; DSR, see D. Johnson and D. Maltz, “Protocols for Adaptive Wireless and Mobile Networking,” IEEE Pers. Commun., Vol. 3, No. 1, February 1996; TORA, see V. Park and M. Corson, “A Highly Adaptive Distributed Routing Algorithm for Mobile Wireless Networks,” Proc. IEEE INFOCOM 97, Kobe, Japan, April 1997; SSA, see R. Dube et al., “Signal Stability-Based Adaptive Routing (SSA) for Ad Hoc Mobile Networks,” IEEE Pers. Commun., February 1997; and ZRP, see Z. Haas and M. Pearlman, “The Zone Routing Protocol for Highly Reconfigurable Ad Hoc Networks,” Proc. ACM SIGCOMM 98, Vancouver, British Columbia, August 1998). The Dynamic Source Routing (DSR) protocol has been shown to out perform many other on-demand routing protocols. J. Broch et al, “A Performance Comparison of Multi-Hop Wireless Ad Hoc Network Routing Protocols,” Proc. ACM MOBICOM 98, Dallas, Tex., October 1998. The existing on-demand routing protocols differ on the specific mechanisms used to disseminate flood-search packets and the responses thereto, the means used to cache information received during other nodes' searches, and the manner in which to determine the cost of a link and the existence of a neighbor. However, one common characteristic of all of the on-demand routing protocols reported to date is that such protocols are based on distances to destinations. Stated differently, there have been no on-demand link-state routing protocol proposals to date.

[0006] In a table-driven scheme, each router maintains path information for each known destination in the network and updates its routing-table entries as needed. Examples of table-driven algorithms based on distance vectors are the routing protocol of the DARPA packet-radio network, J. Jubin and J. Tornow, “The DARPA Packet Radio Network Protocols,” Proceedings of the IEEE, Vol. 75, No. 1, January 1987; DSDV, C. Perkins and P. Bhagwat, “Highly Dynamic Destination-Sequenced Distance-Vector Routing (DSDV) for Mobile Computers,” Proc. ACM SIGCOMM 94, London, UK, October 1994; WRP, S. Murthy and J. J. Garcia-Luna-Aceves, “An Efficient Routing Protocol for Wireless Networks,” ACM Mobile Networks and Applications Journal, Special issue on Routing in Mobile Communication Networks, 1996; WIRP, J. J. Garcia-Luna-Aceves et al., “Wireless Internet Gateways (WINGS),” Proc. IEEE MILCOM'97, Monterey, Calif., November 1997; and least-resistance routing protocols, M Pursley and H. B. Russell, “Routing in Frequency-Hop Packet Radio Networks with Partial-Band Jamming,” IEEE Trans. Commun., Vol. 41, No. 7, pp. 1117-1124, 1993.

[0007] Prior table-driven approaches to link-state routing in packet-radio networks are based on topology broadcasts. However, disseminating complete link-state information to all routers incurs excessive communication overhead in an ad hoc network because of the dynamics of the network and the small bandwidth available. Accordingly, all existing link-state routing approaches for packet-radio networks have been based on hierarchical routing schemes. R. Ramanathan and M. Steenstrup, “Hierarchically-organized, Multihop Mobile Wireless Networks for Quality-of-Service Support,” ACM Mobile Networks and Applications, Vol.3, No. 1, pp. 101-119, 1998; C. V. Ramamoorthy and W. Tsai, “An Adaptive Hierarchical Routing. Algorithm,” Proceedings of IEEE COMPSAC '83, Chicago, Ill., pp. 93-104, November 1983; and M. Steenstrup (ed.), Routing in Communication Networks, Prentice-Hall, 1995. Also, prior proposals for link-state routing using partial link-state data without clusters, see, e.g., J. J. Garcia-Luna-Aceves and J. Behrens, “Distributed, scalable routing based on vectors of link states,” IEEE Journal on Selected Areas in Communications, Vol. 13, No. 8, 1995; and J.J. Garcia-Luna-Aceves and M. Spohn, “Scalable Link-State Internet Routing,” Proc. IEEE International Conference on Network Protocols (ICNP 98), Austin, Tex., Oct. 14-16, 1998, require routers to explicitly inform their neighbors which links they use and which links they stop using.

[0008] A number of prior routing protocols are based on the notion of routing trees, in which routers communicate either the state (i.e., cost or length) of the links in a shortest-path routing tree, or the distance from the root of the tree and the second-to-last hop in the routing tree for each node in the tree. An early example of this type of protocol was proposed in U.S. Pat. No. 4,466,060 to Riddle. In Riddle's protocol, a router communicates different routing trees to different neighbors; such trees are called “exclusionary trees” and specify the preferred paths to destinations excluding those paths that involve the router to which the update is being sent. An update packet or message specifies an entire exclusionary tree. Another protocol based on routing trees was reported by Garcia-Luna-Aceves, J. J. Garcia-Luna-Aceves, “A Fail-Safe Routing Algorithm for Multihop Packet-Radio networks,” Proc. IEEE Infocom 86, Miami, Fla., April 1986, which protocol differs from Riddle's protocol in that the same routing tree is sent incrementally by a router to all its neighbors. A. Humblet, “Another Adaptive Shortest-Path Algorithm,” IEEE Trans. Comm., Vol.39, No.6, June 1991, pp.995-1003 (and see U.S. Pat. No. 4,987,536); Cheng et al., C. Cheng et al., “A Loop-Free Extended Bellman-Ford Routing Protocol without Bouncing Effect”, Proc. ACM SIGCOMM 89, pp.224-236; B. Rajagopalan and M. Faiman, “A Responsive Distributed Shortest-Path Routing Algorithm within Autonomous Systems,” Journal of Internetworking: Research and Experience}, Vol. 2, No. 1, March 1991, pp. 51-69; and S. Murthy and J.J. Garcia-Luna-Aceves, “Loop-Free Internet Routing Using Hierarchical Routing Trees,” Proc. IEEE INFOCOM 97, Kobe, Japan, Apr. 7-11, 1997, have all proposed protocols based on source trees in which a router communicates to its neighbors the same shortest-path routing tree incrementally and these latter examples differ from the above-cited protocol by Garcia-Luna-Aceves in the way in which a router obtains its own source tree from the trees reported by its neighbors. An important feature of all prior routing tree-based protocols is the fact that they are all based on communicating routing trees in terms of the lengths of the links and the identifiers of the nodes that form part of the routing trees.

SUMMARY OF THE INVENTION

[0009] In one embodiment of the present scheme, one or more labeled routing trees (LRTs) are produced at a router of a computer network according to a shortest path determination made over a partial topology graph of the network, which graph is produced according to knowledge of adjacent links of the router and one or more LRTs of neighboring routers. The LRTs of the router may be updated in response to receipt of routing state update messages, and such messages may include local link identifiers assigned by a head of a link to which the identifiers pertain, and node parameters of a tail of the link to which the local link identifiers pertain. The routing state update messages may be transmitted within the network: (i) in response to a new destination node being detected by an existing node within the network, (ii) in response to a destination becoming unreachable by a collection of the existing nodes, (iii) in response to the change in the cost of a path to at least one destination exceeding a threshold delta, and/or (iv) in situations where a routing loop may be encountered among two or more of the nodes of the network (e.g., at times when a path implied in the LRT of the router leads to a loop).

[0010] In another embodiment, the present routing protocol allows for distributing local link identifiers among nodes of a computer network within routing state update messages. These local link identifiers are preferably assigned by a head of a link to which the identifiers pertain. The routing state update messages may include state parameters for nodes at tails of links to which the identifiers pertain. The routing protocol may further provide for distributing labeled routing trees of the nodes of the computer network among the nodes, for example wherein each node of the computers network may distribute its labeled routing trees to its neighboring nodes.

[0011] In such a routing protocol each node of the computer network preferably maintains one labeled routing tree per type of service offered in the network. These labeled routing trees may be generated according to a partial topology graph derived from the node's adjacent links and labeled routing trees of neighboring nodes, for example by applying a path selection algorithm to the partial topology graph. The labeled routing trees may then be updated in response to receipt of the routing state update messages. Such updates may be made according to either an optimum routing approach or a least overhead routing approach, depending upon which approach is used within the computer network.

[0012] For the optimum routing approach, routing state update messages are preferably transmitted: (i) when a routing state update message which causes a link to be added to a subject node's labeled routing trees is received, (ii) when a more recent routing state update message regarding an existing link in the subject node's labeled routing trees is received, and/or (iii) when a destination becomes unreachable by the subject node. In the least overhead routing approach, routing state update messages may be transmitted: (i) when a subject node finds a new destination or any neighbors of the subject node report same, (ii) when a destination becomes unreachable by the subject node or any of its neighbors, (iii) when the subject node finds that the change in the cost of a path to at least one destination exceeds a threshold delta, (iv) when a path implied in any of the labeled routing trees of the subject node leads to a loop, and/or a new successor chosen to a given destination has an address larger than an address of the subject node and a reported distance from the new successor to a particular destination is larger than a reported distance from a previous successor to that particular destination. Another embodiment provides a routing update message that includes information regarding performance characteristics and addressing information for a link of a computer network and a node of the network at a tail end of the link. In some cases, the routing update may further include a time stamp assigned by a node at a head end of the link, a type of service vector, and addressing information for the node at a head end of the link. The performance characteristics preferably include link state parameters (e.g., link delay, link cost, available bandwidth, and/or reliability) of the link, while the type of service vector preferably specifies a type of service routing tree in which the link is being used by a node transmitting the routing update message. The addressing information of the link is preferably specified in the form of a local link identifier assigned to the link by the node at a head end of the link.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The present invention is illustrated by way of example, and not limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements and in which:

[0014]FIG. 1 illustrates an example of an ad hoc wireless network with routers configured in accordance with the present routing protocol;

[0015]FIGS. 2a-2 d illustrate an example of a six-node wireless network with routers configured in accordance with the present routing protocol and the labeled routing trees developed at various ones of the routers;

[0016]FIGS. 3a-3 f illustrate an example of a six-node wireless network with routers configured in accordance with the present routing protocol and the routing state updates generated after certain link failures within the network; and

[0017]FIGS. 4a-4 f illustrate an example of how a link failure within a wireless network made up of a number of routers configured in accordance with the present routing protocol may not lead to the generation of new update messages by such routers when all such routers still have a path to all available destinations in the network.

DETAILED DESCRIPTION

[0018] A scheme for enabling routing of data packets in a computer network along preferred paths either on a hop-by-hop basis, or by specifying a source route efficiently by means of local identifiers is disclosed herein. Although discussed with reference to certain illustrated embodiments, upon review of this specification, those of ordinary skill in the art will recognize that the present scheme may find application in a variety of systems. Therefore, in the following description the illustrated embodiments should be regarded as exemplary only and should not be deemed to be limiting in scope.

[0019] In the present scheme, each packet being routed carries a routing operation code (ROC) instructing the receiving router which routing method to apply to forward the packet. A packet can be forwarded in any of the following forwarding modes: (a) a conventional hop-by-hop routing mode, which uses the routing table of the router; or (b) a source-routing mode, in which the entire source route is specified in the packet using local link identifiers instead of the addresses of relay routers as is common in prior source routing approaches. These forwarding modes are enabled using the present routing protocol, termed the Adaptive Internet Routing (AIR) protocol, which allows for the dissemination of link-state information and node-state information in the form of labeled routing trees (LRTs).

[0020] With AIR, a router sends updates to its neighbors regarding the links and nodes in its preferred paths to destinations. The links and nodes along the preferred paths from a source to each desired destination constitute an LRT that implicitly specifies the complete paths from the source to each destination. Each link is labeled with a local link identifier (LLID).

[0021] Each link in an LRT is directed and has a head-of-link node and a tail-of-link node. The head of the link labels the link with an LLFD that differentiates that link from all other links from the same node to other neighbors. The LLID of a link is much smaller (in terms of the number of bits required to specify the LLID) than the address of a node.

[0022] Each router maintains an LRT for each type of service defined in the network (e.g., minimum-hop, minimum delay, and maximum bandwidth paths of the smallest number of hops). Each router also maintains a routing or topology graph that includes the state information about adjacent links and the LRTs reported by its neighbors. Each router computes its LRT for a given type of service based on the link and node information available in its topology graph.

[0023] A router reports changes to any of its LRTs to all its neighbors incrementally or atomically. The rules used to decide when a router should communicate changes to the state of a node or link can be based on optimum routing or least overhead routing approaches. The aggregation of adjacent links and routing trees reported by neighbors then constitutes the partial topology known by a router. To minimize the number of times the state of a link is communicated to neighbors, a router may assign a type vector to each link, with each bit of the vector indicating in which LRT the link is being used by the router.

[0024] AIR does not require backbones, the dissemination of complete cluster topology within a cluster, or the dissemination of the complete inter-cluster connectivity among clusters. Furthermore, AIR can be used with distributed hierarchical routing schemes proposed in the past for either distance-vector or link-state routing. See, e.g., L. Kleinrock and F. Kamoun, “Hierarchical Routing for Large Networks: Performance Evaluation and Optimization,” Computer Networks, Vol. 1, pp. 155-174, 1977; M. Steenstrup (ed.), Routing in Communication Networks, Prentice-Hall, 1995; S. Murthy and J. J. Garcia-Luna-Aceves, “Loop-Free Internet Routing Using Hierarchical Routing Trees,” Proc. IEEE INFOCOM 97, Kobe, Japan, Apr. 7-11, 1997; and J. Behrens and J. J. Garcia-Luna-Aceves, “Hierarchical Routing Using Link Vectors,” Proc. IEEE INFOCOM 98, San Francisco, Calif., Mar. 29-Apr. 2, 1998.

[0025] A router chooses its preferred paths for a given type of service using a local path-selection algorithm. One preferred path-selection algorithm for use according to the present scheme is a modification of the shortest-path first (SPF) algorithm. The result of running the path-selection algorithm over the topology graph is an LRT for a given type of service that specifies, for each node in the LRT: the address of the head of the link incident to the node, the state parameters of the link, the state parameters of the node, and the LLID assigned to the link by the head of the link. Of course, other path selection algorithms may be used to provide similar outputs.

[0026] From its LRT, a router can compute a source route to a given destination. Because links are labeled with LLIDs assigned by the head of the links, a router can uniquely specify a source route to a destination using its own address followed by a sequence of LLIDs corresponding to its preferred path to the destination, rather than as a sequence of much larger network or link-level addresses. Although source routing and the use of local link identifiers have been used independently of one another in routing and bridging protocols in the past, AIR is the first routing protocol that disseminates the LLIDs of links, thus allowing a compact specification of source routes, making much more efficient use of the available bandwidth.

[0027] The present routing scheme is thus well suited for an ad hoc network that provides a seamless extension of the Internet Protocol (IP) to the ad hoc wireless environment. AIR will be described in terms of its operation in internet radios or IRs, which are wireless routers. However, it will be evident to those of ordinary skill in the art that AIR applies to computer networks and inter-networks that need not be based on wireless links for router interconnection. FIG. 1 illustrates aspects of an exemplary ad hoc internet that will assist in understanding the remaining discussion.

[0028] Ad hoc network 10 may be considered as a number of sub-networks 12 a, 12 b, 12 c, which provide an extension of the Internet 14 through a number of Internet Radios or IRs 16 a-16 i. Each IR 16 a-16 i is a wireless router with an assigned IP address and a medium access control (MAC) address. In general, IRs 16 a-16 i operate over one or a multiplicity of radio channels using spread-spectrum wireless communication techniques common in the art. For example, the IRs 16 a-16 i may operate in one of the unregulated UHF frequency bands, thereby obviating the need for operating licenses. Coupling of ad hoc network 10 to the Internet 14 is achieved through a router 18, which may be operated by an Internet Service Provider (ISP). As shown, a single ISP may operate a LAN 20 to which multiple IRs are connected. In such a scheme, IRs 16 a and 16 b may act as “AirHeads”, providing gateway service to Internet 14 via router 18. Some IRs, e.g., IRs 16 d and 16 e of FIG. 1, may be associated with hosts, 22 a, 22 b and 22 c, which can be accessed by any Internet user through ad hoc network 10. Like any router, each IR 16 a-16 i processes all messages, changes in the cost of an adjacent link, adjacent-link failures, and new-neighbor notifications one at a time and in the order in which it detects them.

[0029] Any IR 16 a-16 i in FIG. 1 can consider another IR to be adjacent (we call such an IR a “neighbor”) if there is radio connectivity between the two IRs and one IR, e.g., IR 16 g, can receive and acknowledge packets from the other IR, e.g., IR 16 h. Accordingly, a physical broadcast link connecting multiple IRs is mapped into multiple point-to-point bidirectional links defined for the same IRs. Each pair of adjacent IRs defines two point-to-point bidirectional links between them, one in each direction. Each point-to-point bidirectional link has a head node of the link and a tail node of the link.

[0030] The present routing scheme can be brought to practice together with the methods described in co-pending U.S. application Ser. No. 09/248,738, entitled “Adaptive Communication protocol for Wireless Networks,” filed Feb. 10, 1999, and assigned to the Assignee of the present invention, incorporated herein by reference, for the assignment of logical link identifiers by one node to each of its one-hop neighbors. However, it will be evident to those of ordinary skill in the art that the present scheme can make use of any link-level service that enables a router to use a local identifier for each of its one-hop neighbors. The description of the present routing scheme thus assumes the existence of local identifiers for the links between a router and its immediate neighbors.

[0031] An underlying protocol, the above-noted neighbor protocol, assures that each IR 16 a-16 i detects within a finite time the existence of a new neighbor IR and the loss of connectivity with a neighbor IR. The neighbor protocol assumed in the present scheme can be brought to practice using link-layer retransmission strategies common in the art.

[0032] I. AIR Operation

[0033] In AIR, each IR reports to its neighbors the characteristics of every link and IR it uses to reach a destination in the ad hoc network. The set of links and IRs used by an IR in its preferred path to destinations is called the LRT of the IR. If multiple types of service (TOS) are defined in the network, an IR maintains one LRT per TOS. An IR therefore knows its adjacent links and the LRTs reported by its neighbors for each TOS, and the aggregation of an IR's adjacent links and the LRTs reported by its neighbors constitutes a partial topology graph. The links in the LRT and topology graph should be adjacent links or links reported by at least one neighbor. An IR may use the topology graph to generate its own LRT for each TOS. Each IR derives its LRT and routing table specifying the successor to each destination for each TOS by running a local path-selection algorithm for each TOS on its topology graph.

[0034] An IR communicates the updates it makes to its routing tree for any TOS. Because each IR communicates its routing tree for each TOS to its neighbors, the deletion of a link no longer used to reach a destination for a given TOS is implicit with the addition of the new link used to reach the destination and need not be sent explicitly as an update; an IR makes explicit reference to a failed link only when the deletion of a link causes the IR to have no paths to one or more destinations, in which case the IR cannot provide new links to make the deletion of the failed link implicit.

[0035] The basic update unit used in AIR to communicate changes to routing trees is the routing-state update (RSU), which describes the state of a link and the node at the end of the link. The head node of a link is the only IR that can report changes in the parameters of that link. RSUs are validated using sequence numbers, and each IR erases a link from its topology graph if the link is not present in the routing trees of any of its neighbors.

[0036] The operation of AIR can be described formally by pseudocode. As with any such description, however, there are various equivalent formulations that, upon review of the code provided, will be evident as being equivalent thereto to someone of ordinary skill in the art. The pseudocode description is set forth at the end of this detailed description, and the following variables and expressions are used therein:

[0037] T: a constant defining the number of Types of Service (TOS) in the network

[0038] Delta[T]: Delta [0], Delta [1], . . . , Delta [T-1] is a vector corresponding to thresholds to changes in the cost of a path to a destination for a given TOS.

[0039] AGEOUT_INTERVAL:a constant defining the time a failed link stays in the Topology Graph before being aged-out

[0040] ORA:a constant, TRUE if AIR is running under the Optimum Routing Approach

[0041] LORA:a constant, TRUE if AIR is running under the Least Overhead Routing Approach

[0042] TG_(i):Topology Graph at router i

[0043] LRT_(i):Current Labeled Routing Tree at router i

[0044] LRT_(I)′:Labeled Routing Tree created the last time an update message was generated by i

[0045] N_(i):set of neighbors of router i

[0046] NS_(i):set to TRUE if i has not sent its Labeled Routing Tree to a neighbor

[0047] M_(i):set to TRUE if i must report changes to the Labeled Routing Tree

[0048] T_(i):system time used to generate time stamps to RSU_(s)

[0049] (u, v, llid, t; 1[T], {n}, tos[T], del):An entry for link (u, v) in TG_(i), LRT_(i), TG^(i) _(k), and LRT^(i) _(k), where kεN_(i) and {I}={llid, 1[T], tos[T], del}.

[0050] u:Network address of the head of the link

[0051] v:Network address of the tail of the link

[0052] llid:Local link identifier

[0053] t:timestamp

[0054] 1[T]:1[0], 1[1], . . . , 1[T-1] is a vector corresponding to the performance parameters of the link. The parameter 1[0] corresponds to the cost of the link, the remaining parameters may be delay, bandwidth, and reliability of the link, etc.

[0055] {n}:The state parameters of router v

[0056] tos[T]:tos[0], tos[1], . . . , tos[T-1] is the Type of Service bit-vector. A bit x is set to 1 when the link is added to the Labeled Routing Tree with TOS x.

[0057] del:Set to TRUE if the link cannot be used in the computation of the Labeled Routing Trees

[0058] (d[T], pred[T], suc[T], d′[T], d″[T], suc′[T], nbr): Variables assigned to a vertex v in TG_(i), LRT_(i), TG^(i) _(k), and LRT^(i) _(k), where kεN_(i)

[0059] d[T]:Cost of the path i→v in Labeled Routing Tree x; ∀xε[0; T-1]

[0060] pred[T]:Predecessor (link) of vertex v in Labeled Routing Tree x; ∀xε[0; T-1]

[0061] suc[T]:Next-hop towards vertex v in Labeled Routing Tree x; ∀xε[0; T-1]

[0062] d′[T]:Previous distance to v reported by suc′[T]

[0063] d″[T]:Cost of the path i→v the last time the cost of the path changed by Δ[T]

[0064] suc′[T]:Previous successor towards v in Labeled Routing Tree x; ∀xε[0; T-0 1]

[0065] nbr:Set to i if the cost of the path to v has increased but no update message must be generated

[0066] (u, v, llid, t, 1[T], {n}, tos[T]): Entry in an update message (RSU)

[0067] u:Network address of the head of the link

[0068] v:Network address of the tail of the link

[0069] llid:Local link identifier

[0070] t:Time stamp assigned to RSU

[0071] 1[T]:Vector corresponding to the performance parameters of the link

[0072] {n}:The state parameters of router v

[0073] tos[T]:Type of Service bit-vector

[0074] The pseudocode specifies the main procedures of AIR used to update the routing table and the link-state database at a router i for both an Optimum Routing Approach (ORA) and a Least Overhead Routing Approach (LORA). Procedure NodeUp is executed when a router i starts up. The neighbor set of the router is empty initially.

[0075] If the neighbor protocol reports a new link to a neighbor k (procedure {\em NeighborUp), the router then runs Update with the appropriate message as input; the RSU in the message gets a current time stamp. The same approach is used for link failures (NeighborDown) and changes in the parameters of a link (LinkChange). When a router establishes connectivity to a new neighbor, the router sends its complete labeled routing tree to the neighbor (much like a distance vector protocol sends its complete routing table). The RSUs that are to be broadcast to all neighbors are inserted into MSG_(i).

[0076] The procedure Update is executed when router i receives an update message from neighbor k or when the parameters of an outgoing link have changed. First, the topology graphs TG_(i) and TG^(i) _(k) are updated, then the labeled routing trees LRT^(i) _(k) and LRT_(i) are updated, which may cause the router to update its routing table and to send its own update message.

[0077] The state of a link in the topology graph TG_(i) is updated with the new parameters for the link if the routing-state update in the received message is valid, i.e., if the RSU has a larger time stamp than the time stamp of the link stored in TG_(i).

[0078] The parameters of a link in TG^(i) _(k) are always updated when processing an RSU sent by a neighbor k, even if the link-state information is outdated, because they report changes to the labeled routing tree of the neighbor. A node in a labeled routing tree LRT^(i) _(k) for a given TOS can have only one link incident to it. Hence, when i receives an RSU for link (u,v) from k the current incident link (u′, v) to v, u≠u′, is deleted from TG^(i) _(k).

[0079] The information of an RSU reporting the failure of a link is discarded if the link is not in the topology graph of the router.

[0080] A shortest-path algorithm (SPF) based on Dijkstra's SPF (procedure BuildShortestPathTree) is run on the updated topology graph TG^(i) _(k) to construct a new labeled routing tree LRT^(i) _(k), and then run on the topology graph TG_(i) to construct a new labeled routing tree LRT_(i).

[0081] The incident link to a node v in router's i new labeled routing tree is different from the link in the current labeled routing tree LRT_(i) only if the cost of the path to v has decreased or if the incident link in LRT_(i) was deleted from the labeled routing trees of all neighbors.

[0082] A new labeled routing tree newLRT for a neighbor k, including the router's new labeled routing tree, is then compared to the current labeled routing tree LRT^(i) _(k) (procedure UpdateNeighborTree), and the links that are in LRT^(i) _(k) but not in newLRT are deleted from TG^(i) _(k). After deleting a link (u, v) from TG^(i) _(k) the router sets TG_(i)(u, v).del to TRUE if the link is not present in the topology graphs TG^(i) _(x), γXεN_(i).

[0083] If a destination v becomes unreachable, i.e., there is no path to v in the new labeled routing tree newLRT, then RSUs will be broadcast to the neighbors for each link in the topology graph TG_(i) that have v as the tail node of the link and a link cost infinity.

[0084] This specification assumes that the Link Layer provides reliable broadcast of network-level packets and consequently update messages specify only incremental changes to the router's labeled routing tree instead of the complete labeled routing tree.

[0085] The new router's labeled routing tree newLRT is compared to the last reported labeled routing tree ({LRT_(i)}′ for LORA and LRT_(i) for ORA) (procedure ReportChanges), and an update message that will be broadcast to the neighbors is constructed from the differences of the two trees. An RSU is generated if the link is in the new labeled routing tree but not in the current labeled routing tree, or if the parameters of the link have changed. For the case of a router running LORA, the labeled routing trees are only compared with each other if at least one of the four rules described in section V, below, is met, i.e., M_(i)=TRUE.

[0086] If the new router's labeled routing tree was compared against the last reported labeled routing tree then the router removes from the topology graph all the links that are no longer used by any neighbor in their labeled routing trees (failed links are only removed from the topology graph by agine).

[0087] Finally, the current shortest-path tree LRT^(i) _(k) is discarded and the new one becomes the current labeled routing tree. The router's labeled routing tree is then used to compute the new routing table, using for example a depth-first search in the shortest-path tree.

[0088] II. Information Exchanged in AIR

[0089] Prior routing protocols based on topology information or distance information are based on the parameters of links exclusively. In contrast, AIR uses an update unit that conveys information about the performance characteristics and addressing information for a link and the node at the end of the link. More specifically, an RSU includes the following elements:

[0090] a) A time stamp that validates the RSU;

[0091] b) A type-of-service vector;

[0092] c) The network address of the head node of the link;

[0093] d) The network address of the tail node of the link;

[0094] e) The link state parameters of the link between the two IRs; and

[0095] f) The node state parameters of the tail of the link.

[0096] An update message sent by an IR contains at least one RSU. The time stamp of the RSU is assigned by the head of the link and should not be altered by any other node relaying the RSU in an update message. The type-of-service (TOS) vector is a bit vector specifying the TOS routing tree in which the link is being used by the node sending the RSU. The state parameters of a link are specified as a list of tuples, with each tuple consisting of a type and a content. There are two classes of state parameters for a link: performance parameters and addressing parameters. The performance of a link can be characterized in terms of its delay, cost, bandwidth, and reliability, for example. An addressing parameter specifies an identifier assigned to the link. An example of such an identifier in the present scheme is the local link identifier (LLID) assigned to the link by the head of the link. The state parameters of the tail of a link may include, for example, the remaining battery life of the node.

[0097] III. Information Stored in AIR

[0098]FIGS. 2a-2 d illustrate the fact that IRs running AIR need maintain only partial topology information. These illustrations provide an example of a six-node wireless network (each node labeled a-f, respectively). For simplicity, these Figures assume that a single link parameter is used to characterize a link in one of its directions, called the “cost” of the directed link. For example, link 32 c may have a cost of 5 in the direction b to c, but only a cost of 1 in the direction c to b. In other examples, nodes may be coupled by multiple links between them, each having the same or different costs. FIGS. 2b through 2 d show the selected topology according to AIR at the IRs indicated with filled circles. Solid lines represent the links that are part of the labeled routing tree of the respective IR. Arrowheads on links indicate the direction of the link stored in the IR's topology graph. IR a's labeled routing tree shown in FIG. 2b is formed by the labeled routing trees reported by its neighbors b and c, and the links for which IR a is the head node (namely links (a, b) and (a, c)). Similarly, FIG. 2c shows the LRT for IR b and FIG. 2d that for IR c. From the figures, the savings in storage requirements should be clear, even for this few-node network.

[0099] The information maintained by an IR to participate in AIR includes a topology graph, an LRT for each TOS defined in the network, a routing table, and an adjacent-link table. The record entry for the link from u to v in the topology graph consists of the tuple (u, v, t, {1}, {n}), where u and v are the network addresses of the head and tail of the link, respectively, t is the most recent time stamp received for link (u, v), {1} is a sequence of type-value pairs specifying link parameters, and {n} is a sequence of type-value pairs specifying node parameters. A link parameter used in the present scheme is the LLID of the link.

[0100] The routing table specifies, for each destination and for each TOS, the next IR in the path to the destination and the distance to that destination based on the distance metric used for the TOS.

[0101] The cost of a failed link is considered to be infinity for any TOS. There are various ways in which costs may be assigned to links for a given TOS known in the art. For example, the cost of a link could simply be the number of hops, or the addition of the latency over the link plus some constant bias.

[0102] IV. Validating Updates

[0103] Because of delays in the IRs and links of an internetwork, update messages sent by a IR may propagate at different speeds along different paths. Therefore, a given IR may receive an RSU from a neighbor with stale link-state information, and a distributed termination-detection mechanism is necessary for a IR to ascertain when a given RSU is valid and avoid the possibility of RSUs circulating forever. AIR uses time stamp to validate RSUs. An IR either maintains a clock that does not reset when the IR stops operating, or asks its neighbors for the oldest known time stamp after if initializes or reboots.

[0104] An IR receiving an RSU accepts the RSU as valid if the received RSU has a larger time stamp than the time stammp of the RSU stored from the same source, or if there is no entry for the link in the topology graph and the RSU is not reporting an infinite cost. Link-state information for failed links are the only RSUs erased from the topology graph due to aging (which may be on the order of an hour or so (or other time period) after having processed the RSU). RSUs for operational links are erased from the topology graph when the links are erased from the routing trees of all the neighbors.

[0105] It is noted that, because RSUs for operational links never age out, there is no need for the head node of a link to send periodic RSUs to update the time stamp of the link. This is important, because it means that AIR does not need periodic update messages to validate link-state information like OSPF, J. Moy, “OSPF Version 2,” RFC 1583, Network Working Group, March 1994, and all prior protocols based on sequence numbers or time stamps.

[0106] V. Exchanging Update Messages

[0107] An IR sends RSUs in two different ways: (a) Following an optimum routing approach; and (b) following a least overhead approach. The optimum routing approach is well suited for networks with fairly static topologies. The least overhead approach is tailored for networks with dynamic topologies due to IR mobility. Which approach should be executed in IRs can be defined by an IR configuration parameter.

[0108] As indicated in the pseudocode description, according to the optimum routing approach an IR sends RSUs about a link in the following cases: (a) when an RSU is received for the link causing the link to be added to the IR's routing tree, (b) when the link is already in the IR's routing tree and a more recent RSU is received for the link, (c) when an RSU reporting the failure of the link results in no path to the tail of the link, and (d) when a failed link is not in the IR's routing tree and there is no path to the tail of the link.

[0109] In contrast, according to the least overhead approach an IR sends RSUs according to the following rules:

[0110] (a) The IR finds a new destination, or any of its neighbors reports a new destination.

[0111] (b) The IR finds that the change in the cost of a path to at least one distination exceeds a threshold delta, or at least one destination becomes unreachable to the IR or any of its neighbors.

[0112] (c) A path implied in the LRT of the IR leads to a loop.

[0113] (d) The IR sends an RSU when: (i) The new successor chosen to a given destination has an address larger than the address of the IR; and (ii) the reported distance from the new chosen successor n to a destination j is longer than the reported distance from the previous successor to the same destination. However, if the link from the IR to j fails and n is a neighbor of j, no update message is needed regarding j or any destination whose path from the IR involves j.

[0114] Each time an IR processes an update message from a neighbor, it updates that neighbor's LRT and traverses that tree to determine for which destinations its neighbor uses the IR as a relay in its preferred paths. The IR then determines if it is using the same neighbor as a relay for any of the same destinations. A routing loop is detected if the IR and neighbor use each other as relay to any destination, in which case the loop must be broken and the IR must send an update message with the corresponding changes.

[0115] We observe that, in any routing loop among IRs with unique addresses, one of the IRs must have the smallest address in the loop; therefore, if an IR is forced to send an update message when it chooses a successor whose address is larger than its own, then it is not possible for all IRs in a routing loop to remain quiet after choosing one another, because at least one of them is forced to send an update message, which causes the loop to break when IRs update their LRTs.

[0116] To ensure that AIR works correctly with least overhead routing and incremental updates specifying only changes to an LRT, an IR must remember the LRT that was last notified to its neighbors. If any of the rules for update notification in least overhead routing are satisfied, the IR must do one of two things: (a) If the LRT includes new neighbors than those present in the LRT that was last updated, then the IR must send its entire LRT in its update, so that new neighbors learn about all the destinations the IR knows; (b) if the two LRTs imply the same neighbors, the IR sends only the updates needed to obtain the new LRT from the old one.

[0117] To ensure that AIR stops sending update messages, a simple rule can be used to determine which IR must stop using its neighbor as a relay, such a rule can be, for example, “the IR with the smaller address must change its path.”

[0118] The rules for update-message exchange according to least overhead routing stated above assume that an update message is sent reliably to all the neighbors of an IR. The following example illustrates a scenario in which the last rule is needed to prevent permanent loops. Consider the six-node wireless network 30 shown in FIG. 2a. In this example, IRs are given identifiers that are lexicographically ordered, i.e., “a” is the smallest identifier and “f” is the largest identifier in the graph. All links and nodes are assumed to have the same propagation delays, all the links but links (a, b) and (b, c) have unit cost, and delta=∞. FIGS. 2b through 2 d show the LRTs according to AIR at the IRs indicated with filled circles for the network topology depicted in FIG. 2a. Arrowheads on solid lines indicate the direction of the links stored in the IR's LRT.

[0119]FIGS. 3a-3 f now depict the sequence of events triggered by the execution of AIR in the example network after the failures of links (c, d) 32 g and (b, e) 32 d. The figures show the RSUs (in parentheses) generated by the node with filled circle, which RSUs are transmitted in an update message to the node's neighbors. The third element in an RSU corresponds to the cost of the link (a RESET has cost infinity). As shown in FIG. 3b, node c transmits an RSU after processing the failure of link (c, d) 32 g; the distance from the new successor b to d and f is longer than from the previous successor d. When link (b, e) 32 d fails (see FIG. 3d), node b realizes that the destinations d, e, and f are unreachable and generates an RSU reporting the failure of the link connecting to the head of the subtree of the LRT that becomes unreachable. The RSU from b triggers the RSUs that allow nodes a, b, and c to realize that there are no paths to d, e, and f (FIGS. 3e and 3 f). A similar sequence of events takes place at the other side of the network partition (not shown).

[0120] As another example of the operation of AIR, consider the seven-node wireless network 40 shown in FIG. 4a. All links and nodes are assumed to have the same propagation delays, all the links have unit cost, delta=∞. FIGS. 4b through 4 d show the LRTs produced according to AIR at the IRs indicated with filled circles for the network topology depicted in FIG. 4a. Arrowheads on solid lines indicate the direction of the links stored in the IR's LRT. When the link (f, g) fails (FIG. 4e), the neighbor protocol at node f triggers the execution of procedure NeighborDown, the link (d, g) is inserted into f's LRT but no update message is generated because f's new successor towards g has an address smaller than f and destination g is a neighbor of the new successor. FIG. 4f shows the new LRT of node d after the failure of link (d, g). Because d has an address smaller than the new successor towards g it is required to send an update message reporting the new link added to the LRT. Nodes c, e, and f do not generate any update message after processing d's message because there exist a path to all destinations in the network and no routing loop was formed. This example thus illustrates how link failures may not cause the generation of update messages by nodes that have the failed link in their LRTs as long as the nodes have a path to all destinations.

[0121] VI. Obtaining LRTs and Source Routes

[0122] Obtaining the LRTs and source routes in the present scheme is done with a very simple modification to Dijkstra's SPF algorithm that is run on the topology graph of an IR. The modifications to SPF consist of checking for the proper bit to be set in the TOS bit vector of a link so that only those links being used for the required TOS are considered in preferred paths, and accumulating the source route in terms of LLIDs as the topology graph is traversed.

[0123] Given the topology graph, the algorithm proceeds as follows:

[0124] 1. Initialize: 1. Initialize:  Value of TOS bit vector = T  Set IR-set = {root}, where root is the IR running the algorithm.  Dist-to-root = 0  Route-to-root = root  for all IRs other than root set   Dist-to-IR = infinity   Route-to-IR = root  for all IRs neighbors of root   If TOS bit vector = T then    Dist-to-IR = cost of link to IR    Route-to-IR = Route-to-IR U LLID of link to IR 2. Find next IR in IR-set:  Find an IR x not in set such that:  Dist-to-IR = Minimum{Dist-to-IR not in IR-set  considering only links with TOS bit vector = T}  Augment IR-set = IR-set U x  Stop if IR-set contains all IRs 3. Change chosen distance and path:  For each IR y not in IR-set do:  Dist-to-y = Minimum{ Dist-to-y, Dist-to-z + cost of link(z,y)   with z in IR-set and TOS bit vector of (z,y) = T}  Route-to-y = Route-to-z U LLID of (z,y) 4. Repeat Step 2.

[0125] Thus a scheme for enabling routing of data packets in a computer network has been described. Although the foregoing description and accompanying figures discuss and illustrate specific embodiments, it should be appreciated that the present invention is to be measured only in terms of the claims that follow the example of a pseudocode listing for the routing protocol set forth below: NodeUp( ) description Node i initializes itself {  TG_(i)

;  LRT_(i)

;  LRT′_(i)

;  N_(i)

;  M_(i)

FALSE;  NS_(i)

FALSE; } NeighborUp(k, llid, l[T], {n}) description  Neighbor protocol reports connectivity to neighbor k {  N_(i)

N_(i) ∪ {k};  TG^(i) _(k)

;  LRT^(i) _(k)

;  sendLRT

TRUE;  tos[x]

0, ∀ x ∈ [0,T − 1];  if ( LORA and k ∈ TG_(i) and TG_(i)(k).pred[0] ≠ null )  {   NS_(i)

TRUE;   sendLRT

FALSE;  }  Update(i, (i, k, llid, T_(i), l[T], {n}, tos[T]));  if ( sendLRT )  {   MSG_(i)

;   for each ( link (u, v) ∈ LRT_(i) )    MSG_(i)

MSG_(i) ∪ {( u, v, TG_(i)(u, v).llid,TG_(i)(u, v).t,             TG_(i)(u, v).l[T], TG_(i)(u, v).{n}, TG_(i)(u, v).tos[T])};  }  Send( ); } NeighborDown(k, llid) description  Neighbor protocol reports link failure to neighbor k {  N_(i)

N_(i) − {k};  TG^(i) _(k)

;  LRT^(i) _(k)

;  l[x]

∞, ∀ x ∈ [0, T − 1];  tos[x]

0, ∀ x ∈ [0, T − 1];  Update(i, (i, k, llid, T_(i), l[T], , tos[T]));  Send( ); } LinkChange(k, llid, l[T], {n}) description  Neighbor protocol reports link cost change to neighbor k {  Update(i, (i, k, llid, T_(i), l[T], {n}, TG_(i)(i, k).tos[T]));  Send( ); } Update(k, msg) description  Process update message msg sent by router k {  newLRTi

;  newLRTk

;  UpdateTopologyGraph(k, msg);  for each ( x ∈ [0, T − 1] )   ComputeLabeled RoutingTreeTOS_(x)(k, newLRTi, newLRTk);  if ( k ≠ i )  {   UpdateNeighborTree(k, newLRTk);   LRT^(i) _(k)

newLRTk;   newLRTk

;  }  UpdateNeighborTree(i, newLRTi);  if ( LORA and M_(i) )  {   ReportChanges(LRT′_(i), newLRTi);   LRT′_(i)

newLRTi;   NS_(i)

FALSE;  }  else if ( ORA )   ReportChanges(LRT_(i), newLRTi);  if ( ORA or ( LORA and M_(i) ) )   for each ( link (u, v) ∈ TG_(i) | TG_(i)(u, v).del = TRUE )    TG_(i)

TG_(i) − {(u,v)};  M_(i)

FALSE;  LRT_(i)

newLRTi;  newLRTi

;  UpdateRoutingTable( );  if ( k ≠ i )   Send( ); } UpdateTopologyGraph(k, msg) description  Update TG_(i) and TG_(k) ^(i) from RSUs in msg {  for each ( RSU (u, v, llid, t, l[T], {n}, tos[T]) ∈ msg )  {   if ( l[0] ≠ ∞ )    ProcessAddUpdate(k, (u, v, llid, t, l[T], {n}, tos[T]));   else    ProcessVoidUpdate(k, (u, v, llid, t, l[T], {n}, tos[T]));  } } Send( ) {  if ( MSG_(i) ≠  )   Broadcast message MSG_(i);  MSG_(i)

; } ProcessAddUpdate(k, (u, v, llid, t, l[T], {n}, tos[T])) description  Update topology graphs TG_(i) and TG_(k) ^(i) from RSU (u, v, llid, t, l[T], {n}, tos[T]) {  if ( (u, v) ∉ TG_(i) or t > TG_(i)(u, v).t )  {   if ( (u, v) ∉ TG_(i) )    TG_(i)

TG_(i) ∪ {(u, v, llid, t, l[T], {n}, tos[T])};   else   {    if ( TG_(i)(u, v).l[0] = ∞ )     Link (u, v) is no longer scheduled to age-out;    TG_(i)(u, v).llid

llid;    TG_(i)(u, v).t

t;    TG_(i)(u, v).l[T]

l[T];    TG_(i)(u, v).{n}

{n};   }  }  if ( k ≠ i )  {   for each ( link (r, s) ∈ TG_(k) ^(i) | r ≠ u and s = v )   {    TG_(k) ^(i)(r, s).tos[T]

TG_(k) ^(i)(r, s).tos[T]

(TG_(k) ^(i)(r, s).tos[T] {circumflex over ( )} tos[T]);    if ( TG_(k) ^(i)(r, s).tos[x] = 0, ∀ x ∈ [0, T − 1] )     TG_(k) ^(i)

TG_(k) ^(i) − {(r, s)};   }   if ( (u, v) ∉ TG_(k) ^(i) )    TG_(k) ^(i)

TG_(k) ^(i) ∪{(u, v, llid, t, l[T], {n}, tos[T])};   else   {    TG_(k) ^(i) (u, v).llid

llid;    TG_(k) ^(i) (u, v).t

t;    TG_(k) ^(i) (u, v).l[T]

l[T];    TG_(k) ^(i) (u, v).{n}

{n};    TG_(k) ^(i) (u, v).tos[T]

tos[T];   }  }  TG_(i)(u, v).del

FALSE; } ProcessVoidUpdate(k, (u, v, llid, t, l[T], {n}, tos[T])) description  Update topology graphs TG_(i) and TG_(k) ^(i) from RSU  (u, v, llid, t, l[T], {n}, tos[T]) reporting link failure {  if ( (u, v) ∈ TG_(i) )  {   if ( t > TG_(i)(u, v).t )   {    TG_(i)(u, v).llid

llid;    TG_(i)(u, v).t

t;    TG_(i)(u, v).l[T]

l[T];    TG_(i)(u, v).{n}

{n};    Schedule link (u, v) to age-out in AGEOUT INTERVAL seconds.    The following operation is performed when the link (u, v)    ages out: TG_(i)

TG_(i) − {(u, v)};   }   if ( k ≠ i and (u, v) ∈ TG_(k) ^(i) )   {    TG_(k) ^(i)(u, v).llid

llid;    TG_(k) ^(i)(u, v).t

t;    TG_(k) ^(i)(u, v).l[T]

l[T];    TG_(k) ^(i)(u, v).{n}

{n};    TG_(k) ^(i)(u, v).tos[T]

tos[T];   }   TG_(i)(u, v).del

FALSE;  } } ComputeLabeled RoutingTreeTOS₀ (k, newLRTi, newLRTk) {  if ( k ≠ i )   BuildShortestPathTree(k, newLRTk);  BuildShortestPathTree(i, newLRTi); } BuildShortestPathTree(k, newLR description  Construct LRT^(i) _(k) {  InitializeSingleLabeled Routing(k);  Q

set of vertices in TG_(k) ^(i);  u

ExtractMin(Q);  while ( u ≠ null and TG_(k) ^(i)(u).d[0] < ∞ )  {   if ( TG_(k) ^(i)(u).pred[0] ≠ null and NOT TG_(k) ^(i)(u).pred[0].tos[0] )   {    (r, s)

TG_(k) ^(i)(u).pred[0];    TG_(k) ^(i)(r, s).tos[0]

1;    if ( (r, s) ∉ newLRT )     newLRT

newLRT ∪ (r, s);    newLRT(r, s).tos[0]

1;    if ( LORA and k = i )    {     if ( i > TG_(i)(u).suc[0] )      if ( ∃ x ∈ N_(i) | TG^(i) _(x)(u).suc[0] = i and TG_(i)(u).suc[0] = x )       M_(i)

TRUE;  // LORA-3 rule     if ( TG_(i)(u).suc[0] ≠ TG_(i)(u).suc′[0] and TG_(i)(u).suc[0] > i )      M_(i)

TRUE;  // LORA-3 rule     if ( β (x, y) ∈ LRT′_(i) | y = u and LRT′_(i)(x, y).tos[0] )      M_(i)

TRUE;  // LORA-1 rule     if ( | TG_(i)(u).d[0] − TG_(i)(u).d″[0] | > Δ )     {      M_(i)

TRUE;  // LORA-2 rule      TG_(i)(u).d″[0]

TG_(i)(u).d[0];     }     w

TG_(i)(u).suc[0];     if ( w ≠ i )      path_w_u_cost

TG_(i)(u).d[0] − TG_(i)(i, w).l[0];     else      path_w_u_cost

0;     if ( path_w_u_cost > TG_(i)(u).d′[0] )     {      if ( r = w or TG_(i)(r).nbr = i )       TG_(i)(s).nbr

i;      if ( TG_(i)(s).nbr ≠ i )       M_(i)

TRUE;  // LORA-3 rule     }     TG_(i)(u).d′[0]

path_w_u_cost;     TG_(i)(u).suc′[0]

TG_(i)(u).suc[0];    }   }   for each ( vertex v ∈ adjacency list of TG_(k) ^(i)(u) )   {    TG_(k) ^(i)(u, v).tos[0]

0;    if ( TG_(k) ^(i)(u, v).l[0] ≠ ∞ and NOT TG_(i)(u, v).del )    {     if ( k = i )     {      if ( u = i )       suc

i;      else if ( TG_(i)(u).suc[0] = i )       suc

{x | x ∈ N_(i) and x = u};      else       suc

TG_(i)(u).suc[0];     }     else     {      if ( u = k )       if ( v = i ) suc

i;       else suc

k;      else       suc

TG_(i)(u).suc[0];     }     RelaxEdge(k, u, v, Q, suc);    }   }   if ( Q ≠  ) u

ExtractMin(Q);   else u

null;  } } InitializeSingleLabeled Routing(k) {  for each ( vertex v ∈ TG_(k) ^(i) )  {   TG_(k) ^(i)(v).d[0]

∞;   TG_(k) ^(i)(v).pred[0]

null;   TG_(k) ^(i)(v).suc′[0]

TG_(k) ^(i)(v).suc[0];   TG_(k) ^(i)(v).suc[0]

null;   TG_(k) ^(i)(v).nbr[0]

null;  }  TG_(k) ^(i)(k).d[0]

0; } RelaxEdge(k, u, v, Q, suc) {  if ( TG_(k) ^(i)(v).d[0] > TG_(k) ^(i)(u).d[0] + TG_(k) ^(i)(u, v).l[0] or   ( k = i and TG_(k) ^(i)(v).d[0] = TG_(k) ^(i)(u).d[0] + TG_(k) ^(i)(u, v).l[0] and    (u, v) ∈ LRT_(i) and LRT_(i) (u, v).tos[0] ) )  {   TG_(k) ^(i)(v).d[0]

TG_(k) ^(i)(u).d[0] + TG_(k) ^(i)(u, v).l[0];   TG_(k) ^(i)(v).pred[0]

TG_(k) ^(i)(u, v);   TG_(k) ^(i)(v).suc[0]

suc;   if ( LORA and k = i and TG_(i)(v).suc′[0] = null )   {    // v was an unknown destination    TG_(i)(v).suc′[0]

suc;    TG_(i)(v).d″[0]

TG_(i)(v).d[0];    if ( suc ≠ i )     TG_(i)(v).d′[0]

TG_(i)(v).d[0] − TG_(i)(i, suc).l[0];    else     TG_(i)(v).d′[0]

0;   }   Insert(Q, v);  } } ReportChanges(oldLRT, newLRT) description  Generate RSUs for new links in the router∉s labeled routing tree {  for each ( link (u, v) ∈ newLRT )   if ( (u, v) ∉ oldLRT or newLRT(u, v).t ≠ oldLRT(u, v).t or oldLRT(u, v).tos[T] ≠ newLRT(u, v).tos[T] or NS_(i) )    MSG_(i)

MSG_(i) ∪ {( u, v, TG_(i)(u, v).llid, TG_(i)(u, v).t, TG_(i)(u, v).l[T], TG_(i)(u, v).{n}, TG_(i)(u, v).tos[T])}; } UpdateNeighborTree(k, newLRT) description  Delete links from TG_(k) ^(i) and report failed links {  for each ( link (u, v) ∈ LRT^(i) _(k) )  {   if ( (u, v) ∉ newLRT )   {    // k Has removed (u, v) from its labeled routing tree    if ( LORA and ( TG_(k) ^(i)(v).pred[x] = null, ∀ x ∈ [0, T − 1] ) )    {     // LORA-2 rule: k has no path to destination v     M_(i)

TRUE;     if ( k = i )      for each ( link (r, s) ∈ TG_(i) | s = v )       if ( TG_(i)(r, s).l[0] = ∞ )        MSG_(i)

MSG_(i) ∪ {( r, s, TG_(i)(r, s).llid, TG_(i)(r, s).t, TG_(i)(r, s).l[T], TG_(i)(r, s).{n}, TG_(i)(r, s).tos[T])};    }    if ( ORA and k = i and ( u = i or ( TG_(i)(v).pred[x] = null, ∀ x ∈ [0, T − 1] ) ) )    {     // i has no path to destination v or i is the head node     if ( TG_(i)(v).pred[x] = null, ∀ x ∈ [0, T − 1] )      for each ( link (r, s) ∈ TG_(i)| s = v )       if ( TG_(i)(r, s).l[0] = ∞ )        MSG_(i)

MSG_(i) ∪ {( r, s, TG_(i)(r, s).llid, TG_(i)(r, s).t, TG_(i)(r, s).l[T], TG_(i)(r, s).{n}, TG_(i)(r, s).tos[T])};     else if ( TG_(i)(u, v).l[0] = ∞ )      // i Needs to report failed link      MSG_(i)

MSG_(i) ∪ {( u, v, TG_(i) (u, v).llid, TG_(i)(u, v).t, TG_(i)(u, v).l[T], TG_(i)(u, v).{n}, TG_(i)(u, v).tos[T])};    }    if ( LORA and k = i and ( TG_(i)(v).pred[x] = null, ∀ x ∈ [0, T − 1] ) )    {     TG_(i)(v).d′[x]

∞, ∀ x ∈ [0, T − 1];     TG_(i)(v).suc′[x]

null, ∀ x ∈ [0, T − 1];     TG_(i)(v).d″[x]

∞, ∀ x ∈ [0, T − 1];    }    if ( NOT ( k = i and u = i ) )    {     if ( (u, v) ∈ TG_(k) ^(i) )      TG_(k) ^(i)

TG_(k) ^(i) − {(u, v)};     if ( TG_(i)(u, v).l[0] ≠ ∞ and β x ∈ N_(i)| (u, v) ∈ TG^(i) _(x) )      TG_(i)(u, v).del

TRUE;    }   }  } } 

1-27. (Canceled)
 28. A method for routing information along preferred paths in a computer network in which a plurality of routers are interconnected by communication links, comprising: forming a partial topology graph for a router by combining link-state information of each adjacent link, router-state information of each adjacent router, and link-state information and node-state information of each link adjacent to each adjacent router; and computing a plurality of labeled routing trees (LRT) for the router using only the partial topology graph, each LRT corresponding to a type of service of the computer network, each LRT specifying a preferred path from the router to each of a plurality of destination routers in the network.
 29. The method of claim 28 wherein the LRTs of the router are updated in response to receipt of routing state update messages.
 30. The method of claim 29 wherein the routing state update messages include one or more local link identifiers, each local link identifier assigned by a head-of-link router to which the identifier pertains.
 31. The method of claim 30 wherein the routing state update messages further include router parameters of a tail-of-link router to which a local link identifier pertains.
 32. A source routing protocol, for a computer network in which a plurality of routers are interconnected by communication links, comprising distributing, among the plurality of routers of the computer network, a local link identifier corresponding to each router within routing state update messages, the routing state update messages including a link-state information and a node-state information, wherein each router maintains a plurality of labeled routing tree (LRT), each LRT corresponding to a type of service of the computer network.
 33. The source routing protocol of claim 32 wherein the local link identifiers are each assigned by a head-of-link router to which the identifiers pertain.
 34. The source routing protocol of claim 32 wherein the routing state update messages include state parameters for tail-of-link routers to which the identifiers pertain.
 35. The source routing protocol of claim 32, further comprising distributing labeled routing trees of the routers of the computer network among the routers.
 36. The source routing protocol of claim 35 wherein each router of the computer's network distributes its labeled routing trees to adjacent routers.
 37. The source routing protocol of claim 36 wherein each router of the computer network maintains one labeled routing tree per type of service offered in the network.
 38. The source routing protocol of claim 36 wherein each router generates its labeled routing trees according to a partial topology graph derived from the router's adjacent links and labeled routing trees of neighboring routers.
 39. The source routing protocol of claim 38 wherein the labeled routing trees of a router are generated by applying a path selection algorithm to the partial topology graph, the partial topology graph including a) link-state information of adjacent links and b) link-state information and router-state information of adjacent routers.
 40. The source routing protocol of claim 39 wherein each router maintains a plurality of labeled routing tree (LRT), each LRT corresponding to a type of service of the computer network.
 41. The source routing protocol of claim 40 wherein the labeled routing trees of routers in the computer network are updated in response to receipt of one or more routing state update messages.
 42. The source routing protocol of claim 41 wherein labeled routing trees are updated according to whether an optimum routing approach or a least overhead routing approach is used within the computer network.
 43. The source routing protocol of claim 32 wherein the routing state update message includes performance characteristic information and addressing information for a link of the computer network and a tail-of-link router pertaining to the link.
 44. The source routing protocol of claim 43 wherein the performance characteristics of the link are selected from the group consisting of link delay, link cost, available bandwidth, reliability, and combinations thereof.
 45. The source routing protocol of claim 43 wherein the routing state update message further includes addressing information of the link comprising a local link identifier assigned to the link by a head-of-link router. 